Please don't review just yet.
edit: Okay ready to review.

Hey @zaliqarosli, there isn't any console.logs and I thought we now commit the package-lock.json file. I'm looking at the differences between mine vs the old and it seems that https is now used in mine which is actually better.

@maltheism yeahh unsure about the package-lock. i forgot what we decided after that update PR. @johnsaigle do you remember?

@zaliqarosli #4408

My preference would be to submit updates to .lock files in their own PRs. If you attach them to other PRs it can be a little harder to go back and track changes and discussions.

I don't really deal much with the JS side though so I think you should just go with whatever works best for you all.

Hey @zaliqarosli & @johnsaigle my opinion is we just commit the package-lock.json and literally ignore it in PRs. Reason is every time I run make or npm run compile the file is made and when I go to add files I'm just doing git add * if I'm having a happy day with my workflow. Having to dodge the file by adding all files modified manually is a joke of a life and shouldn't happen much anyway. I think the reason why my package-lock.json using https compared to the old is because I'm using the latest npm and all the other developers never update their toolchain.
Anyway right before publishing release we could checkout 21.0-release, make a pr that just runs npm run compile and commit the package-lock.json file. Otherwise it would be nice to just ignore the file. Whatever the solution happens to be.. I want my git add * command or I'll be more sad in life.

still one more error left on the 'Create New Issue' page

module seems to be working fine now, need to do a proper testing. whatever the solution is for package-lock.json, i don't think it should be included in this PR so i'm still requesting for it to be removed from this PR. if you want to use git add * functionality, you can also easily do git checkout -- package-lock.json after. i personally don't use git add * so this is not any issue i'm invested in, sorry!

Hey @zaliqarosli I'm leaving the package-lock.json in this PR.

Please split this into multiple PRs.. it can't really be reviewed right now, because it doesn't describe what it's fixing, and it's going to conflict with other PRs that are fixing individual problems with the issue tracker.

you can remove the package-lock.json file from this PR now because #4791 takes care of that

As far as I can tell, everything that this PR was trying to do has been fixed in other more targeted PRs now.